System engineering approach applied to Galileo system

Developing a localization system, with more precise performances than GPS that guarantees Europe autonomy is a complex challenge that ESA and a large number of European economical actors of space industry were decided to meet. To design and manage such a huge system would have been impossible without applying System Engineering best practices, thanks to fundamental activities, multidisciplinary teams and dedicated tools. This paper gives an overview of the System Engineering approach applied to design and develop Galileo, the European Satellite Radio-Navigation System. Galileo system scope is so wide that we have decided to focus on some particular steps of the System Engineering processes that are: Requirements Engineering and Architec-ture. All along this paper, examples are given to illustrate the additional difficulties that have made Systems Engineering more and more complex

Inventory Accounting System Using System Engineering Methods

The article presents models of inventory accounting led by a project manager and system engineer. The project “Inventory accounting system using system engineering methods” is aimed at the formation of a separate inventory accounting system in   the development, manufacture and production of products. In the framework of Ural Diesel Engine Plant LLC, such records are kept only for expensive components that are delivered with military acceptance in the context of each contract for each state contract. Even with such accounting at the enterprise, there is a problem of making small profits or lack of profit from the manufacture of military diesel generators. In developing my project, I would like to improve the system of accounting and writing off inventory items supplied with military acceptance, and later using this system for the entire list of components that make up the product. Keywords: systems engineer, project manager, lifecycle, management basics, separate accounting, management accounting, operational accounting, successful accounting syste

User engineering: A new look at system engineering

User Engineering is a new System Engineering perspective responsible for defining and maintaining the user view of the system. Its elements are a process to guide the project and customer, a multidisciplinary team including hard and soft sciences, rapid prototyping tools to build user interfaces quickly and modify them frequently at low cost, and a prototyping center for involving users and designers in an iterative way. The main consideration is reducing the risk that the end user will not or cannot effectively use the system. The process begins with user analysis to produce cognitive and work style models, and task analysis to produce user work functions and scenarios. These become major drivers of the human computer interface design which is presented and reviewed as an interactive prototype by users. Feedback is rapid and productive, and user effectiveness can be measured and observed before the system is built and fielded. Requirements are derived via the prototype and baselined early to serve as an input to the architecture and software design

Engineering psychology: Contribution to system safety

There has been a growing interest in the area of engineering psychology. This article considers some of the major accidents which have occurred in recent years, and the contribution which engineering psychology makes to designing systems and enhancing safety. Accidents are usually multi-causal, and the resident pathogens in the design and operation of human-machine systems can lead to devastating consequences not only for the workers themselves but also for people in the surrounding communities. Specifically, in each of the accidents discussed, operators were unaware of the seriousness of the system malfunctions because warning displays were poorly designed or located, and operators had not been sufficiently trained in dealing with these emergency situations. Since the 1940s machines and equipment have become more complex in nearly every industry. This, coupled with the continuing need to produce effective and safe systems, has resulted in psychology professionals being called to assist in designing even more efficient operating systems. In earlier times, a worker who made a mistake might spoil a piece of work or waste some time. Today, however, a worker's erroneous action can lead to dire consequences

Space shuttle engineering and operations support. Avionics system engineering

The shuttle avionics integration laboratory (SAIL) requirements for supporting the Spacelab/orbiter avionics verification process are defined. The principal topics are a Spacelab avionics hardware assessment, test operations center/electronic systems test laboratory (TOC/ESL) data processing requirements definition, SAIL (Building 16) payload accommodations study, and projected funding and test scheduling. Because of the complex nature of the Spacelab/orbiter computer systems, the PCM data link, and the high rate digital data system hardware/software relationships, early avionics interface verification is required. The SAIL is a prime candidate test location to accomplish this early avionics verification

A system for co-ordinating concurrent engineering

Design of large made-to-order products invariably involves design activities which are increasingly being distributed globally in order to reduce costs, gain competitive advantage and utilise external expertise and resources. Designers specialise within their domain producing solutions to design problems using the tools and techniques with which they are familiar. They possess a relatively local perception of where their expertise and actions are consumed within the design process. This is further compounded when design activities are geographically distributed, resulting with the increased disassociation between an individual designer's activities and the overall design process. The tools and techniques used by designers rarely facilitate concurrency, producing solutions within a particular discipline without using or sharing information from other disciplines, and seldom considering stages within the product's life-cycle other than conceptual, embodiment or detail [1, 2]. Conventional management and maintenance of consistency throughout the product model can subsequently become difficult to achieve since there are many factors that need to be simultaneously considered whilst making achange to the product model

Sail GTS ground system analysis: Avionics system engineering

A comparison of two different concepts for the guidance, navigation and control test set signal ground system is presented. The first is a concept utilizing a ground plate to which crew station, avionics racks, electrical power distribution system, master electrical common connection assembly and marshall mated elements system grounds are connected by 4/0 welding cable. An alternate approach has an aluminum sheet interconnecting the signal ground reference points between the crew station and avionics racks. The comparison analysis quantifies the differences between the two concepts in terms of dc resistance, ac resistance and inductive reactance. These parameters are figures of merit for ground system conductors in that the system with the lowest impedance is the most effective in minimizing noise voltage. Although the welding cable system is probably adequate, the aluminum sheet system provides a higher probability of a successful system design

Re-Engineering of the GSI Control System

After more than 12 years of operation without substantial revision a modernization of the control system at GSI is overdue. A strategy to adapt the system to future needs is outlined. The system has to support a specific environment of which the main features are described. More flexibility than in the current system can be achieved while still using many parts of the actual system.Comment: ICALEPCS 2001, Talk WEAT002, 3 pages, Late

Embedding object-oriented design in system engineering

The Unified Modeling Language (UML) is a collection of techniques intended to document design decisions about software. This contrasts with systems engineering approaches such as for exampleStatemate and the Yourdon Systems Method (YSM), in which the design of an entire system consisting of software and hardware can be documented. The difference between the system- and the software level is reflected in differences between execution semantics as well as in methodology. In this paper, I show how the UML can be used as a system-level design technique. I give a conceptual framework for engineering design that accommodates the system- as well as the software level and show how techniques from the UML and YSM can be classified within this framework, and how this allows a coherent use of these techniques in a system engineering approach. These ideas are illustrated by a case study in which software for a compact dynamic bus station is designed. Finally, I discuss the consequences of this approach for a semantics of UML constructs that would be appropriate for system-level design